Define and validate core capability management stages and system coverage - #658

What changed

Define five management-cycle stages (Strategic, Learning, Planning, Execution, Assurance), independent free-form tags and application-owned technical capabilities as core methodology fields. Add native coverage/date/view settings, additive JSON Schemas and whole-model checks for technical mapping references, local keys, lifetimes and view selections.

The synthetic example includes L1–L3 containment, a horizontal capability, ESG/MDM/Support tags, two systems sharing coverage and dated technical inventory. Existing files may omit the new fields. The methodology version remains unchanged pending release.

Closes #657.

How it is verified

• 11 integration tests with positive/negative subcases, legacy omission, existing fixtures and schema/vocabulary/example parity: python -m unittest discover -s tools/tests -p test_capability_contract.py.
• python tools/tests/test_lint_encoding.py passes.
• 126 tests pass: node --test scripts/check-notations.test.mjs scripts/release-obligations.test.mjs scripts/check-publish-manifest.test.mjs.
• Notation lint, workflow script integrity, publish manifest and git diff --check pass. Notation lint retains four existing advisory warnings.
• Independent draft-07 AJV check accepts nine fixture fragments and rejects four malformed controls.
• CLI 2.11.0 compatibility is documented in guides/capability-map-compatibility.md: file validation skips unavailable maturity sidecars and does not reject malformed new fields. Its acceptance is not claimed as adoption. CLI/DSM/Studio updates and release remain separate.

Checklist

• Based on main, one concern per PR.
• Commits are signed off (git commit -s) — DCO.
• No hub/work-item references in committed files, this description or commit messages.